Skip to content

fix: use detected VM user/home for all provisioning#21

Merged
ethannortharc merged 1 commit intomainfrom
fix/vm-user-detection
Mar 11, 2026
Merged

fix: use detected VM user/home for all provisioning#21
ethannortharc merged 1 commit intomainfrom
fix/vm-user-detection

Conversation

@ethannortharc
Copy link
Copy Markdown
Owner

Summary

  • All post-rebuild provisioning functions (setup_yazi_config, setup_aichat_config, install_latest_claude_code, setup_git_config, setup_ai_tool_configs) now accept vm_user/vm_home parameters from the caller instead of using whoami() internally
  • Fixes claude-code defaulting to opencode on Lima where VM username differs from host (e.g. "ethan.linux" vs "ethan")
  • Applies the same fix to the Ubuntu provisioning path
  • Adds cache_image/cached_image stubs to the Runtime trait for future use

Test plan

  • cargo build succeeds
  • cargo test — all 67 tests pass
  • devbox create on macOS (Lima) — claude-code should be default AI tool
  • devbox create on Linux (Incus) — claude-code should be default AI tool

🤖 Generated with Claude Code

All post-rebuild provisioning functions (yazi, aichat, claude-code,
git config, ai-tool configs) now use detect_vm_username/detect_vm_home
instead of host whoami(). Fixes claude-code defaulting to opencode on
Lima where VM username differs from host (e.g. "ethan.linux" vs "ethan").

Also applies the same fix to the Ubuntu provisioning path and adds
cache_image/cached_image stubs to the Runtime trait for future use.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@ethannortharc ethannortharc merged commit 0f88568 into main Mar 11, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant